Subject: State of the Connect RIGlet address

From: "Steve Klein (254-5623)" <[email-masked]>
Date: Thu, 19 May 94 09:22:10 EDT

In an effort to make some sort of significant progress on our work
before the June AIW, our fearless leader Louise has asked the RIGlet
Coordinators to post a list of proposals and changes already agreed
upon and a list of open items to resolve before we can attain AD status
for release 1.0 of our standard.  The intent of the open items list is
limit the scope of our work over the next few months to only those items
that are part of release 1.0 (and have a chance of completing it).

Here are the lists as I seem them.  Please look them over and give me
any comments on additions or deletions before the end of the day
Friday May 27.  Once the open item list is 'closed', the only items that
will be added are any show stoppers.  After we create THE list, it will
be time to roll up our sleeves and get some meaningful work done before
the June AIW.

Agreements:
- CANUREACH crossovers resolved by comparison of MAC addresses

Open Items:
- consensus on SDLC scenarios for general 'feel' of how SDLC will work
- impact of SDLC to DLC events
- impact of SDLC on FSMs
- support for non-activation XIDs (any opposition to this?)
- propagation of Routing Control Field Largest Frame Bits in SSP messages
- including in the CANUREACH message the frame (TEST, XID) that generated
  it
- agreement on local retries of DLC frames (absorption of retries on
  origin side with local retries on target side)
- obsolete ENTER_BUSY, EXIT_BUSY, TEST_CIRCUIT_REQ, TEST_CIRCUIT response
  commands in SSP Message Type Table and remove them from the FSMs
  (since it looks like these messages are not required for the standard,
   leave them as optional messages that could be supported if desired)

Other work:
- approval of FSM changes for separation of topology and circuit setup
  (Yes I am working on them now.  I am on vacation the rest of the week
   so it will be Monday before they are done.)
- other message crossover situations besides CANUREACHs (see
  Gnanaprakasam Pandian's note dated Mon, 11 Apr 94 15:48:16 PDT)

---

From: Gnanaprakasam Pandian <[email-masked]>
Date: Thu, 19 May 94 10:36:32 PDT

> - including in the CANUREACH message the frame (TEST, XID) that generated

	Could you add RIF type bits to that.
		00 - specific route
		01 - All rings, all routes
		11 - All rings, spanning routes

-- 
G. Pandian           + Gnanaprakasam Pandian      +
Cisco Systems, Inc.  + Software Engineer          +           
1525 O'Brien Drive   + Phone : (415)688-7684      +
Menlo Park,          + FAX   : (415)688-8282      +
CA 94026             + E-mail: [email-masked] +